fix generics treating symchoice symbols as uninstantiated #23860
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #23853
Since #22610 generics turns the
Name
in theGT.Name
expression in the test code into a sym choice. The problem is when the compiler tries to instantiateGT.Name
it also instantiates the sym choice symbols.Name
has typetemplate (E: type ExtensionField)
which contains the unresolved generic typeExtensionField
, which the compiler mistakes as an uninstantiated node, when it's just part of the type of the template. The compilation of the node itself and hence overloading will handle the instantiation of the proc, so we avoid instantiating it insemtypinst
, similar to how the first nodes of call nodes aren't instantiated.